Skip to content

Conversation

@tadamski
Copy link
Contributor

@tadamski tadamski commented Apr 14, 2025

Include the following in the PR:

  • A directory in the form enterprise-beans/4.1 .
  • An index page enterprise-beans/4.1/_index.md following template
  • [x ] Title should be on the form "Enterprise beans 4.1 (under development)"
  • Includes a plan for the release. Usually, a couple of statements is enough. Otherwise, a link to a document describing the release.
  • Includes a detailed description of any backward incompatibility N/A
  • Declares optional features if there are any N/A
  • Includes minimum Java SE version
  • Describe any updates or required changes including splitting out the TCK
  • Link to updated release record

@netlify
Copy link

netlify bot commented Apr 14, 2025

Deploy Preview for jakartaee-specifications ready!

Name Link
🔨 Latest commit 64fcd7c
🔍 Latest deploy log https://app.netlify.com/sites/jakartaee-specifications/deploys/6810abf1e8b743000895b78a
😎 Deploy Preview https://deploy-preview-826--jakartaee-specifications.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@jhanders34
Copy link
Member

@tadamski thank you for creating this draft release plan. Can you update the description to use the template: https://github.com/jakartaee/specifications/blob/master/plan_review_pr_template.md and update things accordingly for the checklist? You do not appear to be a committer for Enterprise Beans, so you cannot create a new release on the project page: https://projects.eclipse.org/projects/ee4j.ejb. You will need to work with a committer in order to get that updated.

@ivargrimstad ivargrimstad added the plan review Use this label on PRs that are filed for plan reviews label Apr 15, 2025
@tadamski
Copy link
Contributor Author

@jhanders34 I have changed the title and mentioned lack of backwards incompatible changes. Are there any more changes necessary?

Copy link

@chengfang chengfang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jhanders34
Copy link
Member

@jhanders34 I have changed the title and mentioned lack of backwards incompatible changes. Are there any more changes necessary?

The description (first comment) still needs to have the checklist that is in the template that I referenced. Copy the raw version of the link in my previous comment and edit the first comment to have that checklist and then checkoff the things on the list that you believe are complete.

One of those checklist items will have you uncomment

* [Jakarta Enterprise Beans 4.1 Release Record](https://projects.eclipse.org/projects/ee4j.ejb/releases/4.0/plan)

and it should point to 4.1 in the link instead of 4.0.

Also you will want to have the line about ratifying implementation and not just Compatible implementation.

@dblevins
Copy link
Contributor

Note to the specification committee, the contents of this PR are still under discussion in the EJB spec group. No plan has yet to be agreed.

@tadamski tadamski changed the title Initial draft of Enterprise Beans 4.1 plan Enterprise beans 4.1 (under development) Apr 15, 2025
@tadamski
Copy link
Contributor Author

@jhanders34 I have updated the description and added release record link (but for now it is invalid because I don't have the rights to create release plan).

@AngeloRubens
Copy link

AngeloRubens commented Apr 16, 2025

Hi All,

why not think about standardizing this implementation present in wildfly? like this:

Ejb Over http/Http2

https://github.com/wildfly/wildfly-http-client/blob/c8f7f52a084714b6c5a5f993ebf2f89ac1f52751/docs/src/main/asciidoc/wire-spec-v3.asciidoc

Distributed EJB Transaction over http/http2

https://developers.redhat.com/articles/2024/08/29/distributed-transactions-jakarta-ee-10-and-wildfly#

@jhanders34
Copy link
Member

@tadamski with Tracy creating the Release Record, are you ready for the release plan to move to the mentor for review and ballot?

@dblevins
Copy link
Contributor

@jhanders34 We've discussed and removed the EJB over HTTP feature. This is now ready to go up for vote.

@dblevins dblevins self-requested a review April 16, 2025 20:57
@tadamski
Copy link
Contributor Author

@jhanders34 yes I'm ok with release plan to move to review and ballot

@ivargrimstad ivargrimstad added the ballot Delivered to the Specification Committee for ballot label Apr 29, 2025
@ivargrimstad ivargrimstad added approved The ballot was approved by the Specification Committee and removed ballot Delivered to the Specification Committee for ballot labels May 7, 2025
@ivargrimstad ivargrimstad merged commit 3b33f1d into jakartaee:master May 7, 2025
5 checks passed
jhanders34 pushed a commit to jhanders34/specifications that referenced this pull request Jun 6, 2025
* Initial draft of Enterprise Beans 4.1 plan

* Update _index.md

---------

Co-authored-by: Ivar Grimstad <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved The ballot was approved by the Specification Committee plan review Use this label on PRs that are filed for plan reviews

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants